@Pravallika21-nama is attempting to deploy a commit to the magic-peach1's projects Team on Vercel.

A member of the Team first needs to authorize it.

👋 Thanks for your PR, @Pravallika21-nama!

Welcome to Reframe — a browser-based video editor built for everyone 🎬

What happens next

1. 🤖 Automated checks — build & TypeScript typecheck will run automatically
2. ✅ Vercel preview — a preview deployment will be created (requires maintainer authorization for fork PRs)
3. 👀 Code review — a maintainer will review your changes
4. 🚀 Merge — once approved, your PR will be merged!

Quick checklist

• PR title follows Conventional Commits (e.g. feat: add dark mode)
• Linked the issue this PR closes (e.g. Closes #123)
• Tested the changes locally (bun run dev)
• Build passes (bun run build)

Useful links

• 📖 CONTRIBUTING.md
• 🐛 Open Issues
• ⭐ Star the repo to support the project!

Happy coding! 🎉

⚠️ PR Format Issues — @Pravallika21-nama

Please fix the following before your PR can be reviewed:

• ⚠️ No linked issue found. Add Closes #<issue-number> to your PR description.

Push new commits after fixing — this comment will update automatically.

📖 CONTRIBUTING.md

Hy @magic-peach please validate and checkout my Pr incase of errors please update the work I would able to work on it
Thanking you

hy @magic-peach please would you check my pr ,incase of changes please ping me

Hy @magic-peach ,please verify

@Pravallika21-nama This PR cannot be merged as-is due to critical issues:

1. Merge conflict markers left in source code — The diff shows literal text clean-final-pr and main embedded inside src/hooks/useVideoEditor.ts. These are unresolved git merge conflict markers that will cause a JavaScript syntax error. You must resolve these properly and remove them.

2. console.log statement added — The PR adds console.log('[Reframe Memory]', ...) inside a useEffect, which violates the contribution guidelines (no console.log statements).

Steps to fix:

1. Remove the leftover conflict marker text (clean-final-pr and main) from useVideoEditor.ts
2. Remove the console.log statement (or the entire memory monitoring useEffect if it was unintentional)
3. Run bun run lint and bunx tsc --noEmit to verify no errors
4. Push the fixed changes

The core fix (null check for TOUR_STEPS[0]) is good — just clean up these issues first!